home *** CD-ROM | disk | FTP | other *** search
- Path: mail2news.demon.co.uk!genesis.demon.co.uk
- From: Lawrence Kirby <fred@genesis.demon.co.uk>
- Newsgroups: comp.lang.c,gnu.gcc.help,comp.unix.programmer
- Subject: Re: Help for using bcopy function
- Date: Sat, 02 Mar 96 15:06:36 GMT
- Organization: none
- Message-ID: <825779196snz@genesis.demon.co.uk>
- References: <4gl53u$4bv@kocrsv08.delcoelect.com> <ELIAS.96Feb27144032@cepheus.omicron.se> <31372F78.167EB0E7@pia.bt.co.uk>
- Reply-To: fred@genesis.demon.co.uk
- X-NNTP-Posting-Host: genesis.demon.co.uk
- X-Newsreader: Demon Internet Simple News v1.27
- X-Mail2News-Path: genesis.demon.co.uk
-
- In article <31372F78.167EB0E7@pia.bt.co.uk>
- alwyn@pia.bt.co.uk "Alwyn Thomas" writes:
-
- >Elias Martenson wrote:
- >
- >> bcopy() is not standard AFAIK. Use memcpy instead.
- >
- >
- >It's certainly standard on SunOS.
-
- That hardly makes it standard. It is not even standard across Unix platforms.
- memcpy and memmove are part of ANSI C which means (comp.lang.c readers
- can skip this!) they are supported on all POSIX.1 compliant systems.
-
- >What the enquirer needs to do is to add the line:
- >
- >extern bcopy();
-
- Only if his system happens to support bcopy. It would be more sensible to
- change to memmove or possibly memcpy.
-
- --
- -----------------------------------------
- Lawrence Kirby | fred@genesis.demon.co.uk
- Wilts, England | 70734.126@compuserve.com
- -----------------------------------------
-